quant serve: portal rules and remote KV (7.4.0) - #298

…to the background

When the --run command exits 0 and its process group is still alive, print
one notice that it moved to the background instead of "stopped (exit code
0)". quant serve already stops the whole group on exit. When only the
--proxy URL still answers, say that quant serve cannot stop that dev
server. A non-zero exit keeps the old message. Windows has no process
group, which the README now says.

The value is stored as a function stores it with secret: true. A function
on quant serve reads it, and a list shows it masked.

quant serve and quant kv --local read optional org, project and meta from
quant/serve.json, so a project without quant.json needs no flags on every
call. A flag still wins, and quant/serve.json wins over quant.json. The
values are validated.

…nt org or project

The quant/serve.json value is used. quant serve prints the warning in the
start-up output, and quant kv --local prints it to stderr.

A yes/no question after the JSON value, default no.

…code

A string error without a message is printed above the old advice (retry
for 409, check URL and scopes for 422). A message still replaces the
advice. deployError moves its text into helpers (complexity 10 or less).

…e stops

stopRun aborts the poll, so it never keeps Node alive after a stop.

set prints the entry with the value [ENCRYPTED], the mask of a list. The
menu asks for a secret value with hidden input. --secret on get, list or
delete prints one notice that it is ignored.

…, --run limits

…ge and proxy rules

The portal client calls an optional onRequest hook for each HTTP attempt,
so readStore counts 429 retries in requests and in maxRequests. A keys page
with has_more and no next_cursor now stops the read as truncated.

…napshot

…place

A rules deploy creates or updates only the manifest rules of its own
namespace and never removes a rule. The merge now drops only a pulled
managed rule whose deploy namespace and id match a rule of
quant/edge-rules.json, and keeps every other pulled rule in its order.

…rors

- One request budget of 200 for the whole start-up, shared by the rules,
  headers and KV reads. The client checks it before each attempt, 429
  retries included, and refuses the attempt once it is spent. The KV
  read then stops as truncated (request limit).
- A 5xx or no answer from the project headers gives one warning and no
  portal global headers instead of a stop. The 403 warning names the
  headers read.
- static_error_page is on for any value that is not empty.
- readStore no longer takes a request count or returns one.

ruleLabel comes from rule-actions.js, listsStatus from rules.js, and
isObject from src/helper/is-object.js. No behaviour change.

Add a docs note that the trailing-slash setting and the edge cache
settings are not pulled.